Skip to content

Date the 2027.1.0 changelog for the release - #72

Merged
serionist merged 2 commits into
mainfrom
64-release-2027-1
Oct 12, 2026
Merged

serionist merged 2 commits into
mainfrom
64-release-2027-1

Conversation

@serionist

Copy link
Copy Markdown
Owner

What and why

Step 6 of the 2027.1.0 epic (#64): every item is merged (#66, #67, #68, #69, #71), so CHANGELOG.md's 2027.1.0 section gets its date, which release.yml requires of a stable tag, and a short intro. It also lists one fix the Physical step made and the changelog missed: the gateway answers 404, not 500, when its provider refuses a download's path between its info and its bytes.

After this merges: tag v2027.1.0-rc.1 on it, approve the nuget deployment, check the prerelease restores from nuget.org, then tag v2027.1.0 the same way (docs/releasing.md).

Plan

docs/plans/2026-10-12-2027-1.md, step 6.

Tested by

Docs only. CI runs every suite on the commit that will be tagged.

Review

Trivial: a date, an intro paragraph and one changelog line. Read against the merged PRs: every consumer-visible change of #66–#71 has its line.

One-way doors

None.

Refs #64

The five additions of the 2027.1.0 epic are merged, so the version's section
gets its date and a short intro, which release.yml requires of a stable tag.
It also lists the gateway's 404 for a path refused mid-download, which the
Physical step added.

Refs #64
@serionist
serionist merged commit 97df989 into main Oct 12, 2026
6 checks passed
@serionist
serionist deleted the 64-release-2027-1 branch October 12, 2026 22:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant